Skip to content

salvage: fix ROS distance max_range mapping (credit @1aal #4908)#9781

Open
Bartok9 wants to merge 1 commit into
microsoft:mainfrom
Bartok9:salvage/ros-distance-max-range-4908-20260715
Open

salvage: fix ROS distance max_range mapping (credit @1aal #4908)#9781
Bartok9 wants to merge 1 commit into
microsoft:mainfrom
Bartok9:salvage/ros-distance-max-range-4908-20260715

Conversation

@Bartok9

@Bartok9 Bartok9 commented Jul 15, 2026

Copy link
Copy Markdown

About

Salvage of #4908 by @1aal — credit to the original author.

ROS1 get_range_from_airsim set sensor_msgs::Range::max_range from dist_data.min_distance, so max equalled min. Correct mapping is max_distance.

Enhancements beyond the original:

  • Rebased cleanly on current main
  • Documented Range min/max field mapping in docs/airsim_ros_pkgs.md
  • Fixed typo “Meausrement” → “Measurement”

ROS2 wrapper already used max_distance (left unchanged).

Fixes

Files

  • ros/src/airsim_ros_pkgs/src/airsim_ros_wrapper.cpp
  • docs/airsim_ros_pkgs.md

How Has This Been Tested?

  • Reviewed third call site pattern; ROS2 twin already correct
  • Docs markdown visual check
  • Full ROS1 stack not run in this environment (micro one-liner semantics)

Notes

Aerial / drone agent campaign salvage slot for microsoft/AirSim.

)

ROS1 airsim_ros_wrapper assigned sensor_msgs::Range::max_range from
min_distance. Map max_range from max_distance instead. Document Range
fields on airsim_ros_pkgs.md and fix a small spelling typo.

Salvage of microsoft#4908 — original fix by @1aal; rebased onto
current main with docs deckle.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant